Microsoft SQL Server

I am a computer engineer. I have been working as a software developer for about 7 years. I've been using Microsoft SQL Server since I was a student. The interface is very simple and useful, even beginners can use it comfortably. The dark theme has no shortcomings except that it is added under options. Table, schema, and index adding operations can be handled with a single line.

We use SQL server as a back-end for the vast majority of our software applications. This includes backends for web apps, data staging and SSIS/SSRS. As far as DB's go, SQL server is our first choice because it integrates easily with our Microsoft .net and .net core applications. Our SQL DB's are used across the entire organization.

We currently use Microsoft SQL Server as our database application for our applications. We are using the Microsoft SQL Server jobs, Analysis services, cubes, and many other features to help provide front end data solutions to our customers. Our instance of Microsoft SQL Server also allows for multi-database implementation with full backup capabilities. We also pair with the latest management studio to get the best UI experience.

We use it as our central data warehouse across the entire organization for most of our data needs. We base our MicroStrategy Analytics software off of it, executive reporting off of it, and use it to house several years of transaction and inventory data. It serves as the central source of truth.

Over in IT we use [Microsoft] SQL Server as our primary RDBMS across the entire department. We have a handful of legacy oracle databases which are yet to be retired and are planned to switch over to [Microsoft] SQL Server. [Microsoft] SQL Server is the database behind all of our software application systems essentially and is how we maintain and store all of our application data.

It is used as a back-end database engine for front-end client databases. Client is installed on user computers and it connects to a Microsoft SQL Server server for data.

For the uninitiated it is first important to point out that many programs use a Database at the back-end and the end-user will be totally unaware of that fact. So Microsoft SQL Server is a Database software. You (or the program you use) can enter all the needed information and then retrieve it when needed.

We use Microsoft SQL Server to provide a platform for our field users to input data for multiple purposes. We store contract data, financial data, time entry data, customer survey data among other data. Microsoft SQL Server gives us a single source of truth for a lot of our reporting. This allows us to have confidence that we are recording and reporting out accurate data.

I currently provide consulting services to various clients. These clients use [Microsoft] SQL Server as the database for there financial system and CRM applications in addition to using for reporting and ETL processes.

Microsoft SQL Server is our organization's main Database Management System and is the primary back-end server for most of our critical business applications. It's a general requirement that any new application we implement has to operate on SQL Server, if it requires a database back-end. We have a great dependency upon SQL Server and it has not disappointed us.

This is the database engine we use for our own systems and for our clients. So we use it internaly and externaly, to store all the information we need to have control of.
Also this is the source for different process and reports, outside the database sich as Power BI.
It helps a lot with the database storing, since it is very easy to use and manage.

We use Microsoft SQL Server as the DB option for the commercial back-office modules of our MLFF (Multi-Lane - Free Flow) Tolling solution. All the commercial back-office (from Customer registration to involvement and payment handling) relies on Microsoft SQL Server databases. Other vital components of the entire solution, like Security and Vehicle Management, and the Reporting environment also utilize Microsoft SQL Server.

Our business's in house desktop and web applications run off a SQL Server database. We have used it (and abused it) for 12 or so years now. I don't personally have experience with other databases (a little MySQL) but so far I haven't come across a scenario where SQL Server has been lacking, and that is coming from someone who advocates putting the business logic in SP's (OK, let's not start down that path...).

We utilize Microsoft SQL Server as the database for our Epicor Prophet 21 ERP system. It is used by all of our users to process the products that we sell, the potential customers for our Sales staff, and our purchasing department to order from suppliers. We also utilize SQL Reporting to create custom SQL reports for Management and end users. Microsoft SQL Server helps address the ability for management to easily query and access necessary business metrics. Customized SQL Server views and stored procedures are used to automate management tracking and customer contact. Since SQL Server is a widely-used database, numerous third-party tools that we use, like Pipedrive and Google BigQuery, easily interface with our data.

I have worked with Microsoft SQL Server on many projects. The most recent was as the backend of an ERP system. The nature of an ERP system involved the entire organization from the shop which would use it to get the BOM (Bill Of Material) to build the parts to QA to check the parts to Purchasing to buy the raw materials to Sales to sell the parts to Shipping to ship the parts and even HR.

Microsoft SQL Server is used in our organization to store data, run analyses, and produce reports using data from our web-based application. It is mostly being used in the data analytics department and it allows the team to work on projects together and integrate with other software used in the organization.

Our company uses MS SQL Server to run jobs, store data and generates reports. Our team is supporting two separate companies and both use MS SQL Server. One is for storing data and running SSIS jobs for app and reporting purposes. These are company-owned servers and we are hosting other companies to provide service, application and hardware support for them.
Our company maintains these servers and they are being used by different departments, also internal company-wide. Business problems that we commonly encountered are mostly connection issues. These are basically a between network, database and applications connecting to MS SQL Server. The MS SQL Server support is easy to get in touch with when we are having issues with the application itself.

My department uses SQL Server (and Azure Data Studio, increasingly, but still primarily SQL Server) for database management and analysis. Other departments use it as well, including our QA team, to verify the expected output of data manipulation or the functionality of changes to the code base. It's a pretty standard tool at this point.

I consult for system and data integration projects. Many of my customers use SQL as their data management and storage system. During integration projects, I will also use SQL to store information that I need later in the integration process or for reporting purposes or auditing.

SQL Server is our go-to database for both on-prem and cloud database needs. We are running on-prem for 3rd party, custom applications, and the enterprise data warehouse. The Cloud is great for custom applications, as well as beginning to migrate to a data lake structure with Azure SQL DW. Other than embedded databases in a few apps, it is the only RDBMS technology we leverage, although we do run several different versions and editions (Azure SQL DB, Azure SQL DW, SQL Server 2016, 2017).

I use Microsoft SQL Server to write SQL queries for my healthcare organization to do reporting for national quality metrics. It allows me to write efficient, fast queries that export nicely to Excel.

In our database department, we use Microsoft SQL Server for storing data, data aggregation, and manipulation. We use Reporting services tools for creating, managing and deploying reports for our clients. For creating a report definition I personally used Report Builder which makes defining data source connections, queries used to retrieve data, expressions, parameters and others extremely easy to perform. We also try to improve the performance of stored procedures, user-defined functions, and triggers by learning the execution plan in detail. One of our clients has a web app for an insurance company and they have a large amount of data stored in the Microsoft SQL Server database. Our goal is to improve performance from queries that are used in that web app, so we try controlling execution plans with hints or adding indexes. In cases when we meet a new client who already has some database storage then we use replication technology for copying and distributing data and objects from one database to another. Besides that, we also help our clients to build parameterized queries in order to defend from SQL injection which is one of the most common web hacking techniques.

We are using Microsoft SQL Server to store the data of many commercial and internal software applications: SAP Business One, our Point of Sale system installed in more than 60 branches around the country, several web and desktop applications, and our data warehouse used across the company. That represents thousands of transactions per day.

We currently use SQL Server in Azure which makes management easier, though I have used on-premises SQL Server for many years, many versions. I am Microsoft certified in SQL Server 2012 and 2014. As a software developer I like the way SQL Server is easy to program against -- especially when using Entity framework or Entity Framework Core as the middle ware. As a database administrator I like the fact that SQL Server is truly relational, which makes it much easier to model business objects as data tables and to manage Referential integrity, locking and consistency. I like its ability to help with performance scaling via pre-compiled queries, stored procedures and triggers. I like its ability to help with scaling via sharing and replication. But above all I love SSMS (SQL Server Management System) which brings together all the tools in one place with easy access to query plan tools and analysis tools as well as SSIS / SSRS allowing integration of data with other systems and generation of reports.
It has matured over the years into a tool that makes life easy for those architecting or writing systems.

We are a Business Intelligence shop utilizing the entire Microsoft Data Stack. We use SQL Server versions 2012, 2014, 2017. We are also currently evaluating 2019. Our entire organization also uses SQL Server. In our department, it is used to ETL data in (via SSIS), store it into a Kimball Data Warehouse, do reporting off of it via SSRS, and then provide self serve analytics to our business users via SSAS. The best thing is that SSIS, SSRS, and SSAS are all included with SQL Server!